5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
- Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 3-17: Using Event Points

Post User Selection


The Post User Selection event point executes after a PCF record is read and satisfies the constraints imposed by the Establish PCF Range event point, and after APPX applies the selection criteria, and only if the record satisfies all selection criteria. This means that this event point only executes for a specific subset of records in the PCF.

This event point can be used to read other files to make values available for sorts, because it only executes for records that satisfy the selection criteria. For example, you might want to sort information in a transaction file that contains a customer number, based upon a customer alpha field that is maintained in a customer file. If you place the routine to retrieve the customer information in this event point, APPX only retrieves the information for transaction records that satisfy the selection criteria, and not for every transaction record in the file.

APPX cannot, however, guarantee that the sort will complete by the time the process that uses the queried records begins. Therefore, you should not use this or any query event point for performing file updates or accumulating file totals.

MENU, INPUT, OUTPUT, INQUIRY, JOB, STATUS, UPDATE, and QUERY statements should not be entered in the Post User Selection event point, and if present they will be ignored at runtime. This is also true for display control statements such as DISPLAY, BLINK, BLANK, NO INPUT, and so forth.

Application Design Manual                                         "Powered by Appx Software"

478

©2006 By APPX Software, Inc. All Rights Reserved